System and method for performing mass renaming of list of items at run-time with variable differentiation factor

ABSTRACT

Systems and methods for performing mass renaming of a list of items at run-time with variable differentiation factors, which may be applied to a management device managing the list of items. The management device provides multiple predetermined dynamic keys for the list of items to be renamed, where each of the predetermined dynamic keys has a corresponding differentiating value for each item. For example, properties of the items may be used as the predetermined dynamic keys. Then, the management device may receive an instruction from a user for renaming the list of items. The instruction may include information for selecting at least one of the predetermined dynamic keys to be used in the renaming process. In response to the instruction, the management device may perform a renaming process at run-time to rename the items using the predetermined dynamic keys being selected.

FIELD

The present disclosure relates generally to automated renamingtechnology, and more particularly to systems and methods for performingmass renaming of a list of items at run-time with variabledifferentiation factors.

BACKGROUND

The background description provided herein is for the purpose ofgenerally presenting the context of the disclosure. Work of thepresently named inventors, to the extent it is described in thisbackground section, as well as aspects of the description that may nototherwise qualify as prior art at the time of filing, are neitherexpressly nor impliedly admitted as prior art against the presentdisclosure.

Generally, renaming a list of items, such as a set of devices in a datacenter management station, could be a tedious process at run timebecause of tens of thousands of devices. Renaming everything at oncecould result in ambiguous entities among the list of items.

Therefore, an unaddressed need exists in the art to address theaforementioned deficiencies and inadequacies.

SUMMARY

Certain aspects of the disclosure direct to a system, which includes amanagement device configured to manage a list of items. The managementdevice includes a processor and a memory storing computer executablecode. The computer executable code, when executed at the processor, isconfigured to: provide a plurality of predetermined dynamic keys for thelist of items, wherein each of the predetermined dynamic keys has acorresponding differentiating value for each item in the list of items;receive an instruction from a user for renaming the list of items,wherein the instruction comprises information for selecting at least oneof the predetermined dynamic keys; and in response to the instruction,rename the items at run-time using the at least one of the predetermineddynamic keys being selected.

Certain aspects of the disclosure direct to a method for performing massrenaming of a list of items at run-time with variable differentiationfactors, which includes: providing, by a management device, a pluralityof predetermined dynamic keys for a list of items, wherein themanagement device is configured to manage the list of items, and each ofthe predetermined dynamic keys has a corresponding differentiating valuefor each item in the list of items; receiving, by the management device,an instruction from a user for renaming the list of items, wherein theinstruction comprises information for selecting at least one of thepredetermined dynamic keys; and in response to the instruction,renaming, by the management device, the items at run-time using the atleast one of the predetermined dynamic keys being selected.

Certain aspects of the disclosure direct to a non-transitory computerreadable medium storing computer executable code. In certainembodiments, the computer executable code, when executed at a processorof a management device, is configured to: provide a plurality ofpredetermined dynamic keys for a list of items managed by the managementdevice, wherein each of the predetermined dynamic keys has acorresponding differentiating value for each item in the list of items;receive an instruction from a user for renaming the list of items,wherein the instruction comprises information for selecting at least oneof the predetermined dynamic keys; and in response to the instruction,rename the items at run-time using the at least one of the predetermineddynamic keys being selected.

In certain embodiments, the system further includes a computing devicecommunicatively connected to the management device via a network,wherein the instruction is received by the management device from thecomputing device.

In certain embodiments, each of the predetermined dynamic keys is aproperty of the items.

In certain embodiments, each of the items is a node, and thepredetermined dynamic keys comprise identification information of thenode.

In certain embodiments, each node is a blade server, and theidentification information comprises a slot identification number of theblade server.

In certain embodiments, the identification information includes: a groupidentification number of the node; an Internet protocol (IP) address ofthe node; a media access control (MAC) address of the node; a model ofthe node; and manufacturer information of the node.

In certain embodiments, the computer executable code, when executed atthe processor, is further configured to: display the predetermineddynamic keys to the user.

In certain embodiments, the instruction further includes information forselecting, from a plurality of lists of items, the list of items to berenamed.

These and other aspects of the present disclosure will become apparentfrom the following description of the preferred embodiment taken inconjunction with the following drawings and their captions, althoughvariations and modifications therein may be affected without departingfrom the spirit and scope of the novel concepts of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure will become more fully understood from thedetailed description and the accompanying drawings, wherein:

FIG. 1 schematically depicts an exemplary system according to certainembodiments of the present disclosure.

FIG. 2 depicts a flowchart of a mass renaming process of a list of itemsat run-time according to certain embodiments of the present disclosure.

FIG. 3 schematically depicts a system where the managed nodes arerenamed as “blade in slot N” by the mass renaming process according tocertain embodiments of the present disclosure.

DETAILED DESCRIPTION

The present disclosure is more particularly described in the followingexamples that are intended as illustrative only since numerousmodifications and variations therein will be apparent to those skilledin the art. Various embodiments of the disclosure are now described indetail. Referring to the drawings, like numbers, if any, indicate likecomponents throughout the views. As used in the description herein andthroughout the claims that follow, the meaning of “a”, “an”, and “the”includes plural reference unless the context clearly dictates otherwise.Also, as used in the description herein and throughout the claims thatfollow, the meaning of “in” includes “in” and “on” unless the contextclearly dictates otherwise. Moreover, titles or subtitles may be used inthe specification for the convenience of a reader, which shall have noinfluence on the scope of the present disclosure. Additionally, someterms used in this specification are more specifically defined below.

The terms used in this specification generally have their ordinarymeanings in the art, within the context of the disclosure, and in thespecific context where each term is used. Certain terms that are used todescribe the disclosure are discussed below, or elsewhere in thespecification, to provide additional guidance to the practitionerregarding the description of the disclosure. For convenience, certainterms may be highlighted, for example using italics and/or quotationmarks. The use of highlighting has no influence on the scope and meaningof a term; the scope and meaning of a term is the same, in the samecontext, whether or not it is highlighted. It will be appreciated thatsame thing can be said in more than one way. Consequently, alternativelanguage and synonyms may be used for any one or more of the termsdiscussed herein, nor is any special significance to be placed uponwhether or not a term is elaborated or discussed herein. Synonyms forcertain terms are provided. A recital of one or more synonyms does notexclude the use of other synonyms. The use of examples anywhere in thisspecification including examples of any terms discussed herein isillustrative only, and in no way limits the scope and meaning of thedisclosure or of any exemplified term. Likewise, the disclosure is notlimited to various embodiments given in this specification.

Unless otherwise defined, all technical and scientific terms used hereinhave the same meaning as commonly understood by one of ordinary skill inthe art to which this disclosure pertains. In the case of conflict, thepresent document, including definitions will control.

As used herein, “around”, “about” or “approximately” shall generallymean within 20 percent, preferably within 10 percent, and morepreferably within 5 percent of a given value or range. Numericalquantities given herein are approximate, meaning that the term “around”,“about” or “approximately” can be inferred if not expressly stated.

As used herein, “plurality” means two or more.

As used herein, the terms “comprising,” “including,” “carrying,”“having,” “containing,” “involving,” and the like are to be understoodto be open-ended, i.e., to mean including but not limited to.

As used herein, the phrase at least one of A, B, and C should beconstrued to mean a logical (A or B or C), using a non-exclusive logicalOR. It should be understood that one or more steps within a method maybe executed in different order (or concurrently) without altering theprinciples of the present disclosure.

As used herein, the term “module” may refer to, be part of, or includean Application Specific Integrated Circuit (ASIC); an electroniccircuit; a combinational logic circuit; a field programmable gate array(FPGA); a processor (shared, dedicated, or group) that executes code;other suitable hardware components that provide the describedfunctionality; or a combination of some or all of the above, such as ina system-on-chip. The term module may include memory (shared, dedicated,or group) that stores code executed by the processor.

The term “code”, as used herein, may include software, firmware, and/ormicrocode, and may refer to programs, routines, functions, classes,and/or objects. The term shared, as used above, means that some or allcode from multiple modules may be executed using a single (shared)processor. In addition, some or all code from multiple modules may bestored by a single (shared) memory. The term group, as used above, meansthat some or all code from a single module may be executed using a groupof processors. In addition, some or all code from a single module may bestored using a group of memories.

The term “interface”, as used herein, generally refers to acommunication tool or means at a point of interaction between componentsfor performing data communication between the components. Generally, aninterface may be applicable at the level of both hardware and software,and may be uni-directional or bi-directional interface. Examples ofphysical hardware interface may include electrical connectors, buses,ports, cables, terminals, and other I/O devices or components. Thecomponents in communication with the interface may be, for example,multiple components or peripheral devices of a computer system.

The terms “chip” or “computer chip”, as used herein, generally refer toa hardware electronic component, and may refer to or include a smallelectronic circuit unit, also known as an integrated circuit (IC), or acombination of electronic circuits or ICs.

The terms “node” or “computing node”, as used herein, generally refer toa basic unit of computer systems. A node may be implemented by aphysical device or a virtual device. For example, a computing devicesuch as a personal computer, a laptop computer, a tablet or a mobiledevice may function as a node. A peripheral device such as a printer, ascanner or a system on chip (SoC) may also function as a node. A virtualdevice, such as a virtual machine (VM), may also function as a node.When defining nodes on the Internet, a node refers to a device or a datapoint having an IP address.

The term “cluster”, as used herein, generally refers to a set of looselyor tightly connected computing devices (or more precisely, computingnodes) that work together such that, in many respects, they can beviewed as a single system. The components of a cluster are usuallyconnected to each other through a network, with each node of the clusterbeing set to perform certain tasks.

Certain embodiments of the present disclosure relate to computertechnology. As depicted in the drawings, computer components may includephysical hardware components, which are shown as solid line blocks, andvirtual software components, which are shown as dashed line blocks. Oneof ordinary skill in the art would appreciate that, unless otherwiseindicated, these computer components may be implemented in, but notlimited to, the forms of software, firmware or hardware components, or acombination thereof.

The apparatuses, systems and methods described herein may be implementedby one or more computer programs executed by one or more processors. Thecomputer programs include processor-executable instructions that arestored on a non-transitory tangible computer readable medium. Thecomputer programs may also include stored data. Non-limiting examples ofthe non-transitory tangible computer readable medium are nonvolatilememory, magnetic storage, and optical storage.

Certain aspects of the present disclosure direct to systems and methodsfor performing mass renaming of a list of items at run-time withvariable differentiation factors on a management device, which isconfigured to manage the items. In certain embodiments, in a managementdevice functioning as a data center management station, the informationof the properties of all the managed node are stored in the managementdevice. Thus, these properties may be used as predetermined dynamickeys, which may be introduced to cause the differentiation factor in therenaming process. In certain embodiments, the predetermined dynamic keyscan be any dynamic values already available in the database of themanagement device, thus allowing users to reuse the information withouthaving to input the names of the managed nodes being renamed over andover again.

FIG. 1 schematically depicts an exemplary system according to certainembodiments of the present disclosure. As shown in FIG. 1, the system100 includes a management device 110, which is specifically configuredto manage a plurality of managed nodes 120. In particular, each of themanaged nodes 120 should have a specific name being stored in themanagement device 110, such that users may recognize the identity ofeach managed node 120 by the name. Optionally, the system 100 mayfurther include a remote computing device 140, which is communicativelyconnected to the management device 110 via a network 130, such that auser may remotely access the management device 110 through the remotecomputing device 140. For example, the management device 110 mayfunction as a server, and the remote computing device 140 may functionas a client, thus forming a client-server system, and a user at theremote computing device 120 may access the management software 142 andother applications provided on the management device 110. In certainembodiments, the network 130 may be a wired or wireless network, and maybe of various forms. Examples of the network 130 may include, but is notlimited to, a local area network (LAN), a wide area network (WAN)including the Internet, or any other type of networks.

The management device 110 is a specialized computing device configuredto manage the managed nodes 120. In certain embodiments, the managementdevice 110 may be a management controller used for specific managementpurposes. Examples of the management device 110 may include a chassismanagement controller, a rack management controller, a virtual machinemanagement controller, a backplane controller, an enclosure managementcontroller, or any other types of management devices. In certainembodiments, examples of the management device 110 may include amicrocontroller based controller, a complex programmable logic device(CPLD) based controller, a field-programmable gate array (FPGA) basedcontroller, or any combination thereof.

As shown in FIG. 1, the management device 110 includes a processor 112,a memory 114, and a storage device 116. Further, the controller 110 mayinclude other hardware components and software components (not shown) toperform its corresponding tasks. For example, the management device 110may include a network interface, such as a network interface card (NIC),which is used to connect the management device 110 to the network 130.Other examples of these hardware and software components of themanagement device 110 may include, but not limited to, other requiredmemory, interfaces, buses, Input/Output (I/O) modules and peripheraldevices.

The processor 112 is the processing core of the management device 110,configured to control operation of the management device 110. In certainembodiments, the processor 112 may be a central processing unit (CPU).In certain embodiments, the processor 112 may execute any computerexecutable code or instructions, such as the firmware 140, themanagement software 142 and the renaming module 144, or otherapplications and instructions of the management device 110. In certainembodiments, the management device 110 may run on more than oneprocessor, such as two processors, four processors, eight processors, orany suitable number of processors.

The memory 114 can be a volatile memory, such as the random-accessmemory (RAM), for storing the data and information during the operationof the management device 110. In certain embodiments, the memory 114 maybe a volatile memory array. In certain embodiments, the managementdevice 110 may run on more than one memory 114.

The storage device 116 is a non-volatile data storage media for storingcomputer executable code or instructions for performing the operation ofthe management device 110. In certain embodiments, the computerexecutable code or instructions of the management device 110 may beimplemented as one or more application programs or modules. Examples ofthe storage device 116 may include non-volatile memory such as flashmemory, non-volatile random-access memory (NVRAM), memory cards, USBdrives, hard drives, floppy disks, optical drives, or any other types ofdata storage devices. In certain embodiments, the management device 110may have multiple storage devices 116, which may be identical storagedevices or different types of storage devices, and the firmware 140, themanagement software 142, the renaming module 144, the data store 146,and other applications or data of the management device 110 may bestored in one or more of the storage devices 116 of the managementdevice 110.

As shown in FIG. 1, the applications and data stored in the storagedevice 116 include the firmware 140, the management software 142, therenaming module 144, and the data store 146. As discussed above, each ofthe firmware 140, the management software 142, the renaming module 144,and the data store 146 may be formed by the computer executable code orinstructions executable at the processor 112. In certain embodiments,each of the firmware 140, the management software 142, the renamingmodule 144, and the data store 146 may further include sub-modules.Alternatively, in certain embodiments, some or all of the firmware 140,the management software 142, the renaming module 144, and the data store146 may be combined to form a single module. In certain embodiments, thestorage device 116 may store other applications independent from thefirmware 140, the management software 142, the renaming module 144, andthe data store 146.

The firmware 140 stored in the storage device 116 includes the computerexecutable code that may be executed at the processor 112 to enable theoperations of the management device 110. In certain embodiments, thefirmware 140 may include one or more modules or software components thatmay be executed independently. In certain embodiments, the managementsoftware 142, the renaming module 144, and the data store 146 may be apart of the firmware 140. In certain embodiments, each of the managementsoftware 142, the renaming module 144, and the data store 146 mayrespectively be a separate software module independent from the firmware140.

The management software 142 is a software application configured toperform management of the managed nodes 120. In certain embodiments,based on the types of the managed nodes 120 being managed by themanagement device 110, the management software 142 may include multiplesoftware modules or sub-modules to provide various different managementfunctions. For example, when the management device 110 is a chassismanagement controller, the management software 142 may include a moduleperforming management of the chassis, and a module performing managementof components such as blade servers, which are installed in the chassis.

The renaming module 144 is a software module configured to provide themass renaming process. In certain embodiments, the renaming module 144may be a part of the management software 142. Alternatively, in certainembodiments, the renaming module 144 may be independent from themanagement software 142.

The data store 146 is a database for storing necessary data of thefirmware 140 and the management software 142. In certain embodiments,the data stored in the data store 146 may include, without being limitedthereto, information of the properties of the managed nodes 120, whichincludes identification information of the managed nodes 120. In certainembodiments, the properties of the managed nodes 120 may be used as thepredetermined dynamic keys in the mass renaming process. Examples of theproperties or identification information of the managed nodes 120 mayinclude, without being limited thereto, a group identification number ofeach node 120, an Internet protocol (IP) address of each node 120, amedia access control (MAC) address of each node 120, a model of eachnode 120, manufacturer information of each node 120, or any other typesof information that may be used to identify the managed nodes 120.

Each of the managed node 120 is an item being managed by the managementsoftware 142 on the management device 110. In certain embodiments, theitems being managed by the management software 142 may not necessarilybe a managed node, but may be in other forms. For example, the itemsbeing managed by the management software 142 may include a plurality ofclusters, and each cluster includes multiple nodes. In certainembodiments, the management software 142 may be used to manage differentlevels of items, such as the nodes and clusters, and each level of itemsmay form a separate list of items.

The remote computing device 140 is a computing device beingcommunicatively connected to the management device 110 via the network130. Examples of the remote computing devices 120 may include, withoutbeing limited to, desktop computers, laptop computers, tablet computers,smartphones, or any other types of computing devices. In certainembodiments, the remote computing device 140 may be one of the managednodes 120 being managed by the management device 110.

As discussed above, the data stored in the data store 146 may includeproperties of the managed nodes 120, which may be used as thepredetermined dynamic keys in the mass renaming process. For example,when the management device 110 is a chassis management controller, abackplane controller or an enclosure management controller that controlsa plurality of blade servers as the managed nodes 120, each blade servermay be installed to the chassis/backplane/enclosure via a correspondingslot. Thus, each blade server may have a corresponding slotidentification number that identifies the corresponding slot, and theslot identification number may be used as the predetermined dynamic key.

FIG. 2 depicts a flowchart of a mass renaming process of a list of itemsat run-time according to certain embodiments of the present disclosure.In certain embodiments, the method as shown in FIG. 2 may be implementedby a system as shown in FIG. 1 for performing a mass renaming process ofa list of items at run-time on a management device 110. In certainembodiments, the items being renamed may be the managed nodes 120, andthe method may be implemented by the renaming module 144 of themanagement device 110 of the system 100 as shown in FIG. 1. It should beparticularly noted that, unless otherwise stated in the presentdisclosure, the steps of the method may be arranged in a differentsequential order, and are thus not limited to the sequential order asshown in FIG. 2.

As shown in FIG. 2, at procedure 210, the management device 110 mayprovide a plurality of predetermined dynamic keys for a list of items(e.g., the managed nodes 120). In certain embodiments, the predetermineddynamic keys may be the properties of the managed nodes 120, which arestored in the data store 146 of the management device 110. For example,when the management device 110 is a chassis management controller, abackplane controller or an enclosure management controller, and themanaged nodes 120 are the blade servers being managed by the managementdevice 110, one of the predetermined dynamic keys may be the slotidentification numbers of the blade servers.

At procedure 220, the management device 110 may display thepredetermined dynamic keys to a user, such that the user understands theformat of each dynamic key to be used in an instruction for renaming theitems (e.g., the managed nodes 120). In certain embodiments, themanagement device 110 may provide a HELP file which is accessible by theuser to show the formats of the dynamic key to be used in theinstruction. For example, when one of the predetermined dynamic keys maybe the slot identification numbers of the blade servers, the user mayinclude a command of <slot-id> in the instruction to indicate the slotidentification number as a selected dynamic key to be used in therenaming process.

At procedure 230, the management device 110 may receive an instructionfrom the user for renaming the list of items (e.g., the managed nodes120). In certain embodiments, a user at the remote computing device 120may type in an instruction to be sent to the management device 110. Forexample, the instruction may include a command of “blade in slot<slot-id>”, indicating that each of the items (blade servers in thiscase) may be renamed as “blade in slot N,” where N is the slotidentification number of each blade server (i.e., the item to berenamed). In certain embodiments, multiple dynamic keys may be used inthe instruction to form a more complicated naming pattern.

In certain embodiments, the instruction may further include informationthat identifies the list of items to be renamed from a plurality oflists of items. For example, when the system also include a plurality ofclusters being formed by the blade servers, the instruction mustidentify whether the blade servers or the clusters are the items to berenamed.

Upon receiving the instruction, at procedure 240, the renaming module144 of the management device 110 may determine whether the instructionidentifies at least one predetermined dynamic key being selected. Forexample, if the instruction includes a command of “blade in slot<slot-id>”, the renaming module 144 may retrieve the information fromthe instruction and identify, from the parameter <slot-id>, that theslot identification number of each blade server is selected as a dynamickey used in the renaming process. If the instruction does not identifyany of the predetermined dynamic key, the process ends. On the otherhand, if the renaming module 144 identifies the predetermined dynamickey (or multiple dynamic keys) to be selected, at procedure 250, therenaming module 144 may perform the mass renaming process at run-timebased on the selected predetermined dynamic key (or dynamic keys). Inthis case, the names of the items (e.g., the blade servers) will beautomatically renamed to become “blade in slot 1,” “blade in slot 2,”etc. FIG. 3 schematically depicts a system where the managed nodes arerenamed as “blade in slot N” by the mass renaming process according tocertain embodiments of the present disclosure. As shown in FIG. 3, themanaged node 120 (i.e., the blade server) having the slot identificationnumber “1” is renamed as “blade in slot 1,” the managed node 120 (i.e.,the blade server) having the slot identification number “2” is renamedas “blade in slot 2,” and the managed node 120 (i.e., the blade server)having the slot identification number “N” is renamed as “blade in slotN.”

In the embodiment as described above, the slot identification number isused as the predetermined dynamic key being selected. Since the slotidentification number for each blade server is a unique number, thesingle predetermined dynamic key being selected would be sufficient forthe mass renaming process. In certain embodiments, however, when otherproperties of the managed nodes 120 are selected as the predetermineddynamic keys in the mass renaming process, it may be necessary to selectmultiple predetermined dynamic keys (e.g., multiple properties of themanaged nodes 120) to avoid duplicate naming problems if it is uncertainwhether each predetermined dynamic key has a unique corresponding valuefor each of the items (i.e., the managed nodes 120) being renamed. Incertain embodiments, the renaming process may further introduce otherparameters as a part of the predetermined dynamic keys to avoidduplicate naming.

In a further aspect, the present disclosure is related to anon-transitory computer readable medium storing computer executablecode. The code, when executed at a processor of a controller, mayperform the method as described above. In certain embodiments, thenon-transitory computer readable medium may include, but not limited to,any physical or virtual storage media storing the firmware of themanagement device. In certain embodiments, the non-transitory computerreadable medium may be implemented as the storage device 116 of themanagement device 110 as shown in FIG. 1.

The foregoing description of the exemplary embodiments of the disclosurehas been presented only for the purposes of illustration and descriptionand is not intended to be exhaustive or to limit the disclosure to theprecise forms disclosed. Many modifications and variations are possiblein light of the above teaching.

The embodiments were chosen and described in order to explain theprinciples of the disclosure and their practical application so as toenable others skilled in the art to utilize the disclosure and variousembodiments and with various modifications as are suited to theparticular use contemplated. Alternative embodiments will becomeapparent to those skilled in the art to which the present disclosurepertains without departing from its spirit and scope. Accordingly, thescope of the present disclosure is defined by the appended claims ratherthan the foregoing description and the exemplary embodiments describedtherein.

What is claimed is:
 1. A system, comprising: a plurality of bladeservers, wherein each of the blade servers has a corresponding slotidentification number; and a management device configured to control theblade servers and manage a list of the blade servers, the managementdevice comprising a processor and a memory storing computer executablecode, wherein the computer executable code, when executed at theprocessor, is configured to: provide a plurality of predetermineddynamic keys for the list of the blade servers, wherein each of thepredetermined dynamic keys for the list of the blade servers comprisesthe corresponding slot identification number of each of the bladeservers; receive an instruction from a user; determine whether theinstruction is a blade server instruction for renaming the list of theblade servers, wherein the blade server instruction comprisesinformation for selecting at least one of the predetermined dynamic keysfor the list of the blade servers; and in response to determining thatthe instruction is the blade server instruction, rename the bladeservers at run-time using the at least one of the predetermined dynamickeys for the list of the blade servers being selected.
 2. The system ofclaim 1, further comprising a computing device communicatively connectedto the management device via a network, wherein the instruction isreceived by the management device from the computing device.
 3. Thesystem of claim 1, wherein each of the predetermined dynamic keys forthe list of the blade servers further comprises identificationinformation of the blade servers.
 4. The system of claim 3, wherein theidentification information of the blade servers comprises: a groupidentification number of each of the blade servers; an Internet protocol(IP) address of each of the blade servers; a media access control (MAC)address of each of the blade servers; a model of each of the bladeservers; and manufacturer information of each of the blade servers. 5.The system of claim 1, wherein the computer executable code, whenexecuted at the processor, is further configured to: display thepredetermined dynamic keys for the list of the blade servers to theuser.
 6. The system of claim 1, wherein the instruction furthercomprises information for selecting, from a plurality of lists of theblade servers, the list of the blade servers to be renamed.
 7. Thesystem of claim 1, wherein the management device is a chassis managementcontroller, a backplane controller or an enclosure management controllercontrolling the blade servers as a plurality of managed nodes.
 8. Thesystem of claim 1, wherein the blade servers form a plurality ofclusters, each of the clusters comprises two or more of the bladeservers, and the computer executable code, when executed at theprocessor, is further configured to: provide a plurality ofpredetermined dynamic keys for a list of the clusters, wherein each ofthe predetermined dynamic keys for the list of the clusters comprisesidentification information of each of the clusters; determine whetherthe instruction is a cluster instruction for renaming the list of theclusters, wherein the cluster instruction comprises information forselecting at least one of the predetermined dynamic keys for the list ofthe clusters; and in response to determining that the instruction is thecluster instruction, rename the clusters at run-time using the at leastone of the predetermined dynamic keys for the list of the clusters beingselected.
 9. A method for performing mass renaming of a list of bladeservers at run-time with variable differentiation factors, comprising:providing, by a management device, a plurality of predetermined dynamickeys for a list of a plurality of blade servers, wherein the managementdevice is configured to control the blade servers and manage the list ofthe blade servers, each of the blade servers has a corresponding slotidentification number, and each of the predetermined dynamic keys forthe list of the blade servers comprises the corresponding slotidentification number of each of the blade servers; receiving, by themanagement device, an instruction from a user; determining, by themanagement device, whether the instruction is a blade server instructionfor renaming the list of the blade servers, wherein the blade serverinstruction comprises information for selecting at least one of thepredetermined dynamic keys for the list of the blade servers; and inresponse to determining that the instruction is the blade serverinstruction, renaming, by the management device, the blade servers atrun-time using the at least one of the predetermined dynamic keys forthe list of the blade servers being selected.
 10. The method of claim 9,wherein the instruction is received by the management device from acomputing device communicatively connected to the management device viaa network.
 11. The method of claim 9, wherein each of the predetermineddynamic keys for the list of the blade servers further comprisesidentification information of the blade servers.
 12. The method of claim11, wherein the identification information of the blade serverscomprises: a group identification number of each of the blade servers;an Internet protocol (IP) address of each of the blade servers; a mediaaccess control (MAC) address of each of the blade servers; a model ofeach of the blade servers; and manufacturer information of each of theblade servers.
 13. The method of claim 9, further comprising:displaying, by the management device, the predetermined dynamic keys forthe list of the blade servers to the user.
 14. The method of claim 9,wherein the instruction further comprises information for selecting,from a plurality of lists of the blade servers, the list of the bladeservers to be renamed.
 15. The method of claim 9, wherein the bladeservers form a plurality of clusters, each of the clusters comprises twoor more of the blade servers, and the method further comprises:providing, by the management device, a plurality of predetermineddynamic keys for a list of the clusters, wherein each of thepredetermined dynamic keys for the list of the clusters comprisesidentification information of each of the clusters; determining, by themanagement device, whether the instruction is a cluster instruction forrenaming the list of the clusters, wherein the cluster instructioncomprises information for selecting at least one of the predetermineddynamic keys for the list of the clusters; and in response todetermining that the instruction is the cluster instruction, renaming,by the management device, the clusters at run-time using the at leastone of the predetermined dynamic keys for the list of the clusters beingselected.
 16. A non-transitory computer readable medium storing computerexecutable code, wherein the computer executable code, when executed ata processor of a management device, is configured to: provide aplurality of predetermined dynamic keys for a list of a plurality ofblade servers managed by the management device, wherein the managementdevice is configured to control the blade servers and manage the list ofthe blade servers, each of the blade servers has a corresponding slotidentification number, and each of the predetermined dynamic keys forthe list of the blade servers comprises the corresponding slotidentification number of each of the blade servers; receive aninstruction from a user; determine whether the instruction is a bladeserver instruction for renaming the list of the blade servers, whereinthe blade server instruction comprises information for selecting atleast one of the predetermined dynamic keys for the list of the bladeservers; and in response to determining that the instruction is theblade server instruction, rename the blade servers at run-time using theat least one of the predetermined dynamic keys for the list of the bladeservers being selected.
 17. The non-transitory computer readable mediumof claim 16, wherein each of the predetermined dynamic keys for the listof the blade servers further comprises identification information of theblade servers.
 18. The non-transitory computer readable medium of claim17, wherein the identification information of the blade serverscomprises: a group identification number of each of the blade servers;an Internet protocol (IP) address of each of the blade servers; a mediaaccess control (MAC) address of each of the blade servers; a model ofeach of the blade servers; and manufacturer information of each of theblade servers.
 19. The non-transitory computer readable medium of claim16, wherein the management device is a chassis management controller, abackplane controller or an enclosure management controller controllingthe blade servers as a plurality of managed nodes.
 20. Thenon-transitory computer readable medium of claim 16, wherein the bladeservers form a plurality of clusters, each of the clusters comprises twoor more of the blade servers, and the computer executable code, whenexecuted at the processor of the management device, is furtherconfigured to: provide a plurality of predetermined dynamic keys for alist of the clusters, wherein each of the predetermined dynamic keys forthe list of the clusters comprises identification information of each ofthe clusters; determine whether the instruction is a cluster instructionfor renaming the list of the clusters, wherein the cluster instructioncomprises information for selecting at least one of the predetermineddynamic keys for the list of the clusters; and in response todetermining that the instruction is the cluster instruction, rename theclusters at run-time using the at least one of the predetermined dynamickeys for the list of the clusters being selected.